Self-Adjusting Connection Pool in a Distributed System

ABSTRACT

A method includes calculating first connection usage information based on a first number of connections being used in a connection pool over a first time interval and adding a first number of database connections to the connection pool based on determining that the first connection usage information satisfies a first usage threshold. Additionally, the method includes calculating second connection usage information based on a second number of connections being used in the connection pool over a second interval. The second interval has been previously reset responsive to adding the first number of database connections to the connection pool. The method also includes determining whether to adjust the number of database connections in the connection pool based on the second connection usage information.

CROSS REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 16/713,833 filed Dec. 13, 2019, the contents of which arehereby incorporated by reference in their entirety for all purposes.

BACKGROUND Technical Field

This disclosure relates generally to database systems and, morespecifically, to adjusting the size of a connection pool in a databasesystem.

Description of the Related Art

Connection pools are used to facilitate access to database system byvarious applications. As such, when an application accesses the databasesystem, the application selects an available database connection fromthe connection pool to connect to the database system. Subsequently,when the database operation(s) initiated by the application is complete,the selected database connection is returned back to the connection poolwhere it is available to be used for another connection to the databasesystem.

In certain instances, the size of the connection pool can include arelatively large number of database connections in order to meet periodof high demand for access to the database system. As a result, however,during period of low demand, many database connections in the connectionpool may remain unused, thereby consuming valuable computing resources.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating an example system for adjustingthe size of a connection pool in a distributed system, according to someembodiments.

FIG. 2 illustrates a diagram illustrating a data flow for adjusting thesize of a connection pool in a distributed system, according to someembodiments.

FIG. 3 illustrates a graph depicting a scenario for operation of theconnection manager, according to some embodiments.

FIG. 4 illustrates a graph depicting another scenario for operation ofthe connection manager, according to some embodiments

FIG. 5 is a flow diagram illustrating a method for adjusting the size ofa connection pool in a database system based on short-term connectionusage information, according to some embodiments.

FIG. 6 is a block diagram illustrating an exemplary computing device,according to some embodiments.

This specification includes references to various embodiments, toindicate that the present disclosure is not intended to refer to oneparticular implementation, but rather a range of embodiments that fallwithin the spirit of the present disclosure, including the appendedclaims. Particular features, structures, or characteristics may becombined in any suitable manner consistent with this disclosure.

Within this disclosure, different entities (which may variously bereferred to as “units,” “circuits,” other components, etc.) may bedescribed or claimed as “configured” to perform one or more tasks oroperations. This formulation—[entity] configured to [perform one or moretasks]—is used herein to refer to structure (i.e., something physical,such as an electronic circuit). More specifically, this formulation isused to indicate that this structure is arranged to perform the one ormore tasks during operation. A structure can be said to be “configuredto” perform some task even if the structure is not currently beingoperated. A “short-term module configured to determine connection usagevalue over a first time interval” is intended to cover, for example, adevice that performs this function during operation, even if thecorresponding device is not currently being used (e.g., when its batteryis not connected to it). Thus, an entity described or recited as“configured to” perform some task refers to something physical, such asa device, circuit, memory storing program instructions executable toimplement the task, etc. This phrase is not used herein to refer tosomething intangible.

The term “configured to” is not intended to mean “configurable to.” Anunprogrammed mobile computing device, for example, would not beconsidered to be “configured to” perform some specific function,although it may be “configurable to” perform that function. Afterappropriate programming, the mobile computing device may then beconfigured to perform that function.

Reciting in the appended claims that a structure is “configured to”perform one or more tasks is expressly intended not to invoke 35 U.S.C.§ 112(f) for that claim element. Accordingly, none of the claims in thisapplication as filed are intended to be interpreted as havingmeans-plus-function elements. Should Applicant wish to invoke Section112(f) during prosecution, it will recite claim elements using the“means for” [performing a function] construct.

As used herein, the term “based on” is used to describe one or morefactors that affect a determination. This term does not foreclose thepossibility that additional factors may affect the determination. Thatis, a determination may be solely based on specified factors or based onthe specified factors as well as other, unspecified factors. Considerthe phrase “determine A based on B.” This phrase specifies that B is afactor and is used to determine A or affects the determination of A.This phrase does not foreclose that the determination of A may also bebased on some other factor, such as C. This phrase is also intended tocover an embodiment in which A is determined based solely on B. As usedherein, the phrase “based on” is synonymous with the phrase “based atleast in part on.”

As used herein, the term “processing element” refers to various elementsconfigured to execute program instructions (or portions thereof orcombinations thereof). Processing elements include, for example,circuits such as an ASIC (Application Specific Integrated Circuit),portions or circuits of individual processor cores, entire processorcores, individual processors, programmable hardware devices such as afield programmable gate array (FPGA), and/or larger portions of systemsthat include multiple processors, as well as any combinations thereof.

DETAILED DESCRIPTION

Techniques are disclosed for an algorithm for adjusting the size of aconnection pool in a database system. In certain embodiments, a databasesystem may be configured to maintain a connection pool to facilitatedatabase connections to a data source. For example, various applicationsmay need to access the data source in the course of normal operations.In order to facilitate the access, a database system may maintain aconnection pool of one or more database connections. As such, each timean application needs to access information from the data source, thedatabase system provides a database connection from the connection poolto the application.

In a typical database system environment, a developer of a firstapplication may set a minimum and maximum number of database connectionsthat can be used by the first application. Another developer of a secondapplication may independently set a minimum and maximum number ofdatabase connections for the second application. In other words, thedevelopers of the first application and second application may beunaware of the connection usage patterns of their respectiveapplications. Thus, in many instances, the developers will set theminimum number of database connections that can be used by theirrespective applications at a relatively high number to ensure that theirrespective applications have adequate access to the database system.This can result in a relatively large number of connections that remainunused, thereby consuming valuable computing resources.

Thus, the present disclosure contemplates a connection manager thatmanages the size of the connection pool in a database system based onconnection usage patterns corresponding to the connection pool.According to certain embodiments, the connection manger may include ashort-term module, a long-term module, and a spike module. Theshort-term module may be configured to sample connection usage oversuccessive time intervals of a first length (e.g., 10 seconds) at afirst sampling rate. At the end of each interval, the short-term moduledetermines whether to adjust a size of the connection pool.

For example, the short-term module may determine the connection usagebased on the samples collected over a first time interval (having thefirst length). Based on the connection usage over the first timeinterval, the short-term module estimates a first connection pool size(e.g., that satisfies the pattern of connection usage over the firsttime interval). If the first connection pool size is greater than thecurrent size of the connection pool, the current size of the connectionpool (e.g., the number of database connections in the connection pool)is then adjusted to match the first connection pool size. In otherimplementations, the connection usage over the first time interval iscompared with a connection usage threshold. If the connection usagesatisfies the connection usage threshold, the connection manager mayincrease the size of the connection pool by a first predetermined numberof database connections.

The long-term module may be configured to sample database connectionusage in the connection pool over a successive time intervals of asecond length (e.g., 10 minutes) at a second sampling rate. The secondlength may be greater than the first length of the time intervalscorresponding to the short-term module. In addition, the second samplingrate may be the same or may be different from the first sampling rate.The long-term module determines whether to adjust the size of theconnection pool at the end of each time interval of the second length.

For instance, the long-term module may determine the database connectionusage based on the samples collected over a second time interval (havingthe second length). Based on the database connection usage of the secondtime interval, the long-term module estimates a second connection poolsize. The size of the connection pool is subsequently adjusted to matchthe second connection pool size.

In other implementations, the database connection usage over the secondtime interval with a threshold usage range having a minimum connectionusage value at a first endpoint and a maximum connection usage value atthe second endpoint. If the database connection usage falls within theconnection usage range (e.g., between the minimum connection usage valueand the maximum connection usage value and inclusive of the minimumconnection usage value and maximum connection usage value), theconnection manager may maintain the current size of the connection pool.If the database connection usage is greater than the maximum connectionusage value, the connection manager increases the size of the connectionpool by a second number of database connections. If the databaseconnection usage is less than the minimum connection usage value, theconnection manager decreases the size of the connection pool (e.g.,reduces the number of database connections in the connection pool) by athird number of database connections. The second and third number ofdatabase connections may be determined by the long-term module based onthe samples collected over the second time interval. In otherimplementations, the second and third number of database connections maybe second and third predetermined number of connections, respectively.

According to a particular embodiment, the operation of the long-termmodule may be affected by the short-term module. For each time intervalthat the short-term module causes the size of the connection pool toincrease, the time interval corresponding to the long-term module isreset. Further, all samples that were collected by the long-term modulebefore the increase in the size of the connection pool are discarded.The long-term module begins a new interval of the second length forsampling the connection usage.

For instance, consider the above examples of the first time intervalsampled by the short-term module and the second time interval sampled bythe long-term module. In this example, the second time interval has beenpreviously reset due to the short-term module increasing the size of theconnection pool based on connection usage in the first time interval.Additionally, any samples collected by the long-term module during theprevious time interval (of the second length) prior to the increase ofthe size of the connection pool are discarded.

According to certain embodiments, the spike module may be configured todetermine when a spike in database connection usage occurs. To this end,the spike module may detect a spike if an increase in databaseconnection usage within a third time interval satisfies a usage increasethreshold. In response to the spike module detecting a spike, theconnection manager may increase the size of the connection pool by anamount estimated by the spike module or a predetermined amount.Additionally, the spike module may associate a decay period with thedetected spike in which the connection manager does not adjust the sizeof the connection pool in response to any subsequently detected spikeswithin the decay period.

FIG. 1 is a block diagram illustrating an example system 100 foradjusting the size of a connection pool in a database system. In theillustrated embodiment, the system 100 includes a database system 102 incommunication with other computer(s) 120 via a network 150. The databasesystem 102 may be configured to dynamically adjust the size of theconnection pool 104 according to connection usage value. It will beappreciated that while FIG. 1 depicts database system 102, in otherembodiments, the database system may be any other type of computersystem, including a distributed computer system.

As used herein, the term “module” refers to circuitry configured toperform specified operations or to physical non-transitory computerreadable media that store information (e.g., program instructions) thatinstructs other circuitry (e.g., a processor) to perform specifiedoperations. Modules may be implemented in multiple ways, including as ahardwired circuit or as a memory having program instructions storedtherein that are executable by one or more processors to perform theoperations. A hardware circuit may include, for example, customvery-large-scale integration (VLSI) circuits or gate arrays,off-the-shelf semiconductors such as logic chips, transistors, or otherdiscrete components. A module may also be implemented in programmablehardware devices such as field programmable gate arrays, programmablearray logic, programmable logic devices, or the like. A module may alsobe any suitable form of non-transitory computer readable media storingprogram instructions executable to perform specified operations.

In FIG. 1, database system 102 may include a connection pool 104, aconnection manager 106, a data source 114, and communication components116. The connection manager 106 may include a short-term module 108, along-term module 110, and a spike module 112. Each of the components ofthe database system 102 may communicate with each other to adjust thesize of a connection pool in a database system, as will be described inmore detail below. Portions of FIG. 1 are described in conjunction withFIG. 2, FIG. 3A, and FIG. 3B.

The connection pool 104 represents a group of database connections(e.g., socket connections to the database system 102) that can be sharedamong various applications accessing the database system 102, such asapplications 122 from other computers 120. For instance, each time anapplication accesses the database system 102 (e.g., to retrieve datafrom the data source(s) 114), the application may connect to thedatabase system 102 via a database connection from the connection pool104. When the application finishes the database operation associatedwith accessing the database system 102, the database connection isreleased back to the connection pool 104 for subsequent use by theapplication or other applications. In this manner, the number ofdatabase connections needed to service database requests from theapplications can be reduced as unused connections from the connection104 can be used and reused as needed.

However, in traditional database systems, the size of the connectionpool can be imprecise relative to the needs of the various applications.For example, in some system environments, developers of differentapplications may program their respective applications to require aminimum number of database connections from the connection pool 104 tobe allocated. Typically, the developers of a particular application areunaware of the traffic patterns (i.e., pattern of use for accessing thedatabase system 102) of the other applications in the systemenvironment. As such, each of the developers may program theirrespective applications to require a relatively high minimum allocationof database connections in order to ensure that the respectiveapplication's functionality with respect to the database system 102.Further, database connections are typically refreshed at certainintervals in order to ensure proper functionality. Refreshing databaseconnections consumes CPU cycles and other computing resources. Thus,since the above described system environment may result in a relativelylarge number of unused database connections at any given moment,valuable computing resources may be wasted by refreshing the unuseddatabase connections.

In order to reduce the number of unused database connections in theconnection pool 104, the connection manager 106 may be configured tomanage the size of the connection pool 104 based on monitoring usage ofthe database connections (e.g., by the applications 122). As previouslydiscussed, the connection manager 106 includes a short-term module 108,a long-term module 110, and a spike module 112. These modules may eachbe configured to monitor the connection usage at respectivepredetermined intervals. The respective predetermined intervals may bethe same or may be different from each other. Moreover, based onoperations of the connection manager 106, the size of the connectionpool 104 may be increased (e.g., one or more connections may be added tothe connection pool 104) or may be decreased (e.g., one or moreconnection may be removed from the connection pool 104).

The short-term module 108 is configured to sample connection usage oversuccessive time intervals of a first length (e.g., 10 seconds) at afirst sampling rate. At the end of each interval of the first length,the short-term module 108 estimates a connection pool size that wouldsatisfy the pattern of connection usage indicated by the collectedsamples. Based on the estimated connection pool size, the short-termmodule 108 determines whether to increase a size of the connection pool104. The long-term module 110 is configured to sample connection usageover successive time intervals of a second length (e.g., 10 minutes)that is greater than the first length. At the end of each interval ofthe second length, the long-term module 110 also estimates a connectionpool size that would satisfy the pattern of connection usage indicatedby its collected samples. Based on the estimated connection pool size,the long-term module 110 determines whether to adjust the size of theconnection pool (e.g., whether to increase, decrease, or maintain thesize). According to a particular embodiment, each time the short-termmodule 108 increases the size of the connection pool 104, the long-termmodule 110 and/or its current time interval at the time of adjustment isreset, and all of the sample collected by the long-term module 110during its current time interval are discarded.

For example, the short-term module 108 determines a first connectionusage value based on sampling connection usage over a first timeinterval of the first length while the long-term module 110 is stillsampling connection usage within a second time interval of the secondlength. Based on the first connection usage value, the short-term module108 estimates a first connection pool size. In some embodiments, thefirst connection usage value may correspond to a moving average of thenumber of connections from the connection pool 104 that are used overthe first time interval (e.g., as indicated by the samples collected bythe short-term module 108).

If the short-term module 108 determines that the first connection poolsize is greater than the current size of the connection pool, theshort-term module 108 causes the connection manager 106 to increase thecurrent size of the connection pool 104 to match the first connectionpool size. Further, the short-term module 108 also causes the long-termmodule 110 to reset (e.g., to have the second time interval for which itis currently sampling connection usage reset). Additionally, any samplesthat have been collected by the long-term module 110 within the secondtime interval are discarded.

The long-term module 110 then begins a third time interval of the secondlength for which to sample the connection usage of the connection pool104. Assuming that the third time interval elapses without the long-termmodule 110 being reset, the long-term module 110 determines a secondconnection usage value based on the samples collected during the thirdtime interval. The long-term module 110 estimates a second connectionpool size based on the second connection usage value. Further, thelong-term module 110 adjusts the current size of the connection pool 104to match the second connection pool size if they are different.

The spike module 112 is configured to periodically monitor connectionusage of the connection pool 104 to identify when spikes in connectionusage occurs. To this end, the spike module 112 is configured todetermine a third connection usage value over another time interval of athird length. The third length may be the same or different from thefirst length of the time intervals associated with the short-term module108 and the second length of the time intervals associated with thelong-term module 110. Further, the spike module 112 estimates a thirdconnection pool size based on its collect samples and increases the sizeof the connection pool 104 to match the third connection pool size.

Additionally, a decay period may also be associated with the spikemodule 112 increasing the size of the connection pool 104. The decayperiod is a time interval occurring immediately after an increase of thesize of the connection pool 104 by the spike module 112. Within thedecay period, the spike module 112 may reduce the size of connectionpool 104 by a predetermined number of connections. In other words, thesize of the connection pool 104 is decreased back to its original sizeimmediately preceding the increase by the spike module 112. Thisreduction in the size of the connection pool 104 during the decay periodmay occur gradually at a specified rate or may be applied all at once atthe end of the decay period. In this manner, the connection manager isable to account for the spike in connection usage while avoiding anoversupply of unneeded connections in the connection pool 104 after thespike has passed.

It will be appreciated that each of the short-term module 108, thelong-term module 110, and the spike module 112 is configured toperiodically sample connection usage at their respective sampling rates.

In some embodiments, the operation of the connection manager 106 and itscomponents (short-term module 108, long-term module 110, and spikemodule 112) can be summarized by the following formula that estimateswhat the size of a connection should be at a given point in time:

${Ec} = {{\underset{\begin{matrix}{T = {c - x}} \\{i = {c - z}}\end{matrix}}{\sum\limits^{c}(L)}\;{{ST}.{Spi}}\;\lambda\underset{\begin{matrix}{t = {c - y}} \\{i = {c - z}}\end{matrix}}{\sum\limits^{c}({SH})}{{St}.{Spi}}} \geq {{\theta\Omega}\;{Spi}}}$

where,

Ec=New overall connection pool size estimate at time c,

Σ(L)=Long-term connection pool size estimate using an adjusted movingavg based on long-term samples ST and spike samples Spi,

Σ(SH)=Short-term connection pool size estimate using an adjusted movingavg based on short-term samples St and spike samples Spi,

ST=Long-term samples collected during the time period T which is theperiod of time represented by c-x (current time c—long-term timeinterval of length x),

St=Short-term samples connection pool size estimate during the timeperiod t which is the period of time represented by c-y (currenttime—short-term interval of length y),

Spi=multiple spike samples collected at time intervals of length i

λ places conditions on Σ(SH) such that: if Σ(SH)<θ, then T=c, whichresets Σ(L) samples. If Σ(SH)>θ, let Σ(L) take effect after X inaddition to Σ(SH),

θ=Current pool size, and

Ω=Applies Independent Spi adjustments for spikes in addition to usingSpi data with Σ(SH) and Σ(L)

The data storage 114 stores various information that the applications122 connect to the database system 102 to access. The data storage mayinclude any type of storage medium, as described in more detail withreference to the storage 612 in FIG. 6.

The communication component 116 may be configured to communicate withvarious other devices, such as the other computer(s) 120 and/or otherdevices. In various embodiments, communication component 116 may includea Digital Subscriber Line (DSL) modem, a Public Switched TelephoneNetwork (PTSN) modem, an Ethernet device, a broadband device, asatellite device and/or various other types of wired and/or wirelessnetwork communication devices including microwave, radio frequency,infrared, Bluetooth, Bluetooth low-energy, near field communication(NFC) devices, and/or the like.

FIG. 1 further illustrates the other computer(s) 120, each of whichincludes applications 122, database 126, and communication component128. As previously discussed, the applications 120 may be any type ofapplication that access the database system 102. According to aparticular embodiment, the applications are applications for backendserver systems maintained by a service provider. The applications areconfigured that access data stored in the database system 102 inresponse to various requests by different components of the backendserver systems.

The network 150 may be implemented as a single network or a combinationof multiple networks. For example, in various embodiments, the network150 may include the Internet or one or more intranets, landlinenetworks, wireless networks, and/or other appropriate types of networks.Thus, the network 150 may correspond to small scale communicationnetworks, such as a private or local area network, or a larger scalenetwork, such as a wide area network or the Internet, accessible by thevarious components of system 100.

FIG. 2 illustrates a data flow diagram 200 of a connection manager 206in accordance with another particular embodiment. As shown in FIG. 2,the connection manager 206 includes a connection usage module 202, ashort-term module 208, a long-term module 210, a spike module 212, andan adjustment module 214.

According to the embodiment illustrated in FIG. 2, the short-term module208, long-term module 210, and spike module 212 may function similarlyto their counterparts illustrated in FIG. 1, except that the adjustmentmodule 214 is configured to make any determination of whether to adjustthe size of the connection pool 104. For instance, the short-term module208 may be configured to periodically (at time intervals of a firstlength) sample short-term connection usage information by communicatingwith the connection usage module 202 (which monitors the connection poolto provide connection usage information) at a first sampling rate. Forexample, the short-term connection usage information indicates a firstnumber of database connections from the connection pool 104 that wereused over a time interval of the first length. For each time interval ofthe first length, the short-term module 208 provides the short-termconnection usage information to the adjustment module 214.

The long-term module 210 may be configured to periodically (at timeintervals of a second length greater than the first length) samplelong-term connection usage information by communicating with theconnection usage module 202 at a second sampling rate. The long-termconnection usage information indicates a second number of databaseconnections from the connection pool 104 that were used over a timeinterval of the second length. For each interval of the second length,the long-term module 210 provides the long-term connection usageinformation to the adjustment module 214.

The spike module 212 may be configured to periodically sample spikeconnection usage information by communicating with the connection usagemodule 202 at a third sampling rate. The spike connection usageinformation indicates a third number of database connections from theconnection pool 104 that were used over a time interval of a thirdlength. For each time interval of the third length, the spike-termmodule 212 provides the spike connection usage information to theadjustment module 214.

It will be appreciated that the first sampling rate may be the same asthe second sampling rate and/or the third sampling rate. In otherimplementations, the first sampling rate may be different from thesecond sampling rate and/or the third sampling rate. Similarly, thesecond sampling rate may be the same as the third sampling rate or inother implementations, may be different than the third sampling rate.

The adjustment module 214 is configured to determine whether to adjustthe size of the connection pool 104 based on the short-term connectionusage information, the long-term connection usage information, and/orthe spike connection usage information. For example, the adjustmentmodule 214 receives connection usage information and determines theusage information type (e.g., short-term connection usage information,long-term connection usage information, or spike connection usageinformation. According to certain embodiments, the adjustment moduledetermines usage information type based on an identifier included in theconnection usage information. In other embodiments, the usageinformation type is determined based on whether the connection usageinformation is received from the short-term module 208, the long-termmodule 210, or the spike module 212.

If the adjustment module 214 determines that the usage information typeof the connection usage information corresponds to short-term connectionusage information, the adjustment module 214 calculates a firstestimated connection pool size based on short-term connection usageinformation. If the first estimated connection pool size is greater thanthe current size of the connection pool, the adjustment module 214increases the current size of the connection pool to match the firstestimated connection pool size. Additionally, the adjustment module 214resets the long-term module 210 (e.g., the time interval of thelong-term module 210) and causes the long-term module 210 discard all ofthe samples collected up to this point. The long-term module 210subsequently begins a new time interval of the second length for whichto sample connection usage of the connection pool 104.

If the adjustment module 214 determines that the usage information typeof the connection usage information corresponds to long-term connectionusage information, the adjustment module 214 calculates a secondestimated connection pool size based on long-term connection usageinformation. The adjustment module 214 then adjusts the current size ofthe connection pool 104 to match the second estimated connection poolsize. This may include increasing, decreasing, or maintaining thecurrent size of the connection pool 104.

If the adjustment module 214 determines that the usage information typeof the connection usage information corresponds to spike connectionusage information, the adjustment module 214 calculates a thirdestimated connection pool size based on spike connection usageinformation. The adjustment module 214 then adjusts the current size ofthe connection pool 104 to match the third estimated connection poolsize.

As previously discussed, a decay period may be initiated subsequent toan increase in the size of the connection pool 104 based on spikeconnection usage information. Within the decay period, the adjustmentmodule 214 may reduce the size of connection pool 104 by a number ofconnections such that at the end of the decay period, the size of theconnection pool 104 may be adjusted back to its size immediatelypreceding the increase based on the spike connection usage information.The adjustment made during the decay period may occur gradually at aspecified rate or may be applied all at once at the end of the decayperiod. In certain embodiments, during the decay period, no otheradjustments may be made to the connection pool 104.

FIG. 3 illustrates an example graph 300 representing connection usageover one or more periods of time according to a particular embodiment.Graph 300 depicts a first time interval 302 between time T1 and T2, asecond time interval 304 between times T1 and T3, and third timeinterval 306 between times T2 and T4. The first time interval 302corresponds to a timeframe considered by a short-term module (e.g.,short-term module 108 and/or short-term module 208), and the second timeinterval 304 corresponds to another timeframe considered by a long-termmodule (e.g., long-term module 110 and/or long-term module 210). Thesecond time interval 304 is the same length of time as the third timeinterval 306.

Based on the connection usage illustrated by graph 300, the short-termmodule causes the size of the connection pool to increase at time T2.Also at time T2, the long-term module, and thus the second time interval304, is reset. As such, any samples of connection usage collected by thelong-term module between times T1 and T2 (e.g., the first time interval302 are discarded). At time T2, the long-term module begins the thirdtime interval 306 for sampling the connection usage. The third timeinterval 306 elapses without being reset. As a result, at time T4, thelong-term module estimates a connection pool size based on the samplesof connection usage collected during the third time interval 306.

FIG. 4 illustrates an example graph 400 representing connection usageover one or more periods of time according to another particularembodiment. Graph 400 depicts a fourth time interval 402 between timesT5 and T6, a fifth time interval 404 between times T5 and T9, and asixth time interval 406 between times T7 and T8. The fourth timeinterval 402 corresponds to a first spike detected by spike module112/212, and the fifth time interval 404 corresponds to a decay periodassociated with the first spike. The sixth time interval 406 correspondsto a second spike detected by the spike module 112/212 within the decayperiod (fifth time interval 404).

Based on the connection usage illustrated by graph 400, the spike module112/212 causes the connection pool to increase in size in response tothe first spike (fourth time interval 402) at time T6. However, sincethe second spike (sixth time interval 406) occurs within the decayperiod (fifth time interval 404), the connection pool size is unchangedin response to the second spike.

FIG. 5 illustrates an example flow diagram of a method 500 for adjustingthe size of a connection pool based on short-term connection usageinformation, according to one or more particular embodiments. The method500 may be performed by a short-term module, such as the short-termmodule 108 of the database system 102 and/or the short-term module 208in combination with the adjustment module 214 of FIG. 2. The methodbegins at step 502, where the short-term module determines short-termconnection usage information over a time interval.

At step 504, the short-term module estimates a connection pool sizebased on the short-term connection usage information. At step 506, theshort-term module determines whether the estimated pool size is greaterthan the current pool size. If not, the method 500 proceeds to step 512where the current size of the connection pool is maintained. If theestimated pool size is greater than the current pool size, at step 508,the short-term module causes the current pool size to be adjusted tomatch the estimated pool size (e.g., to increase the number ofconnections in the connection pool to match the estimated pool size). Atstep 410, the long-term module (e.g., long term module 110/210) to bereset and all the previously collected samples of connection usageinformation by the long-term module to be discarded.

Example Computing Device

Turning now to FIG. 6, a block diagram of one embodiment of computingdevice (which may also be referred to as a computing system) 610 isdepicted. Computing device 610 may be used to implement various portionsof this disclosure including any of the components illustrated in FIG. 1and FIG. 2. Computing device 610 may be any suitable type of device,including, but not limited to, a personal computer system, desktopcomputer, laptop or notebook computer, mainframe computer system, webserver, workstation, or network computer. As shown, computing device 610includes processing unit 650, storage 612, and input/output (I/O)interface 630 coupled via an interconnect 660 (e.g., a system bus). I/Ointerface 630 may be coupled to one or more I/O devices 640. Computingdevice 610 further includes network interface 632, which may be coupledto network 620 for communications with, for example, other computingdevices.

In various embodiments, processing unit 650 includes one or moreprocessors. In some embodiments, processing unit 650 includes one ormore coprocessor units. In some embodiments, multiple instances ofprocessing unit 650 may be coupled to interconnect 660. Processing unit650 (or each processor within 650) may contain a cache or other form ofon-board memory. In some embodiments, processing unit 650 may beimplemented as a general-purpose processing unit, and in otherembodiments it may be implemented as a special purpose processing unit(e.g., an ASIC). In general, computing device 610 is not limited to anyparticular type of processing unit or processor subsystem.

Storage subsystem 612 is usable by processing unit 650 (e.g., to storeinstructions executable by and data used by processing unit 650).Storage subsystem 612 may be implemented by any suitable type ofphysical memory media, including hard disk storage, floppy disk storage,removable disk storage, flash memory, random access memory (RAM-SRAM,EDO RAM, SDRAM, DDR SDRAM, RDRAM, etc.), ROM (PROM, EEPROM, etc.), andso on. Storage subsystem 612 may consist solely of volatile memory, inone embodiment. Storage subsystem 612 may store program instructionsexecutable by computing device 610 using processing unit 650, includingprogram instructions executable to cause computing device 610 toimplement the various techniques disclosed herein.

I/O interface 630 may represent one or more interfaces and may be any ofvarious types of interfaces configured to couple to and communicate withother devices, according to various embodiments. In one embodiment, I/Ointerface 630 is a bridge chip from a front-side to one or moreback-side buses. I/O interface 630 may be coupled to one or more I/Odevices 640 via one or more corresponding buses or other interfaces.Examples of I/O devices include storage devices (hard disk, opticaldrive, removable flash drive, storage array, SAN, or an associatedcontroller), network interface devices, user interface devices or otherdevices (e.g., graphics, sound, etc.).

Various articles of manufacture that store instructions (and,optionally, data) executable by a computing system to implementtechniques disclosed herein are also contemplated. The computing systemmay execute the instructions using one or more processing elements. Thearticles of manufacture include non-transitory computer-readable memorymedia. The contemplated non-transitory computer-readable memory mediainclude portions of a memory subsystem of a computing device as well asstorage media or memory media such as magnetic media (e.g., disk) oroptical media (e.g., CD, DVD, and related technologies, etc.). Thenon-transitory computer-readable media may be either volatile ornonvolatile memory.

Although specific embodiments have been described above, theseembodiments are not intended to limit the scope of the presentdisclosure, even where only a single embodiment is described withrespect to a particular feature. Examples of features provided in thedisclosure are intended to be illustrative rather than restrictiveunless stated otherwise. The above description is intended to cover suchalternatives, modifications, and equivalents as would be apparent to aperson skilled in the art having the benefit of this disclosure.

The scope of the present disclosure includes any feature or combinationof features disclosed herein (either explicitly or implicitly), or anygeneralization thereof, whether or not it mitigates any or all of theproblems addressed herein. Accordingly, new claims may be formulatedduring prosecution of this application (or an application claimingpriority thereto) to any such combination of features. In particular,with reference to the appended claims, features from dependent claimsmay be combined with those of the independent claims and features fromrespective independent claims may be combined in any appropriate mannerand not merely in the specific combinations enumerated in the appendedclaims.

1. (canceled)
 2. A method comprising: receiving connection usageinformation corresponding to a connection pool maintained by a databasesystem, the connection usage information associated with a firsttimeframe; determining an information type corresponding to theconnection usage information; based on the information type, selecting aparticular usage threshold from a set of usage thresholds; and based onwhether the connection usage information satisfies the particular usagethreshold, determining whether to adjust a size of the connection pool.3. The method of claim 2, wherein the information type corresponds to atleast one of a short-term connection usage information, long-termconnection usage information, or a spike connection usage information.4. The method of claim 2, wherein the information type corresponds to ashort-term connection usage information, further comprising: increasingthe size of the connection pool based on the short-term connection usageinformation satisfying the particular usage threshold.
 5. The method ofclaim 2, wherein the information type corresponds to a long-termconnection usage information and the particular usage thresholdcomprises a usage threshold range, and wherein the determining whetherto adjust a size of the connection pool further comprises: comparing thelong-term connection usage information with the usage threshold range.6. The method of claim 2, wherein the connection usage information iscalculated based on sampling connection usage of the connection poolover a first interval at a first sampling rate.
 7. The method of claim2, further comprising: identifying a first spike in network trafficduring an interval; responsive to the identifying, estimating a newconnection pool size for the connection pool based on the first spike;and adjusting a current connection pool size of the connection pool tothe new connection pool size, the new connection pool size being greaterthan the current connection pool size.
 8. The method of claim 7,determining that a predetermined amount of time has elapsed since theidentifying the first spike in the network traffic; and responsive tothe determining, terminating a second number of connections in theconnection pool.
 9. The method of claim 7, further comprising:subsequent to the identifying the first spike in network traffic,identifying a second spike in network traffic; and based on determiningthat the second spike occurred within a predetermined amount of timefrom the first spike, maintaining a previous number of connections inthe connection pool.
 10. The method of claim 2, wherein the determiningwhether to adjust the number of database connections in the connectionpool comprises: estimating a new connection pool size for the connectionpool based on a second connection usage information, the connection poolbeing currently associated with a current pool connection size; andadjusting a number of database connections in the connection pool tomatch the new connection pool size.
 11. A system, comprising: aconnection pool including one or more database connections; a short-termmodule configured to: calculate first connection usage information basedon a first number of connections being used in a connection pool over afirst interval; estimate a first connection pool size based on the firstconnection usage information; a long-term module configured to:calculate second connection usage information based on a second numberof connections being used in a connection pool over a second interval;and estimate a second connection pool size based on the secondconnection usage information; and an adjustment module configured to:responsive to determining that first connection pool size is greaterthan a current number of database connections in the connection pool andprior to calculating the second connection usage information: adjust thecurrent number of database connections to match the first connectionpool size; and reset the long-term module.
 12. The system of claim 11,wherein the adjustment module is further configured to: subsequent toresetting the long-term module, adjust the connection pool to have thesecond connection pool size.
 13. The system of claim 11, wherein thefirst connection usage information is calculated based on samplingconnection usage of the connection pool over the first interval at afirst sampling rate, and wherein the second connection usage informationis calculated based on sampling connection usage of the connection poolover the second interval at a second sampling rate
 14. The system ofclaim 13, wherein the adjustment module is further configured to:discard one or more samples of connection usage information sampled bythe long-term module responsive to determining that first connectionpool size is greater than the current number of database connections inthe connection pool and prior to calculating the second connection usageinformation.
 15. The system of claim 11, wherein the system furthercomprises: a spike module configured to: identifying a first spike innetwork traffic during a third interval; and estimating a thirdconnection pool size for the connection pool based on the first spike,wherein the adjustment module is further configured to: increasing aconnection pool size of the connection pool to the third connection poolsize.
 16. The system of claim 15, wherein the first spike in networktraffic is associated with a decay period in which the connection poolsize cannot be further increased based on subsequently detected spikesin network traffic within the decay period.
 17. A non-transitorycomputer readable medium storing computer-executable instructions thatin response to execution by one or more hardware processors, causes adatabase system to perform operations comprising: receiving connectionusage information corresponding to a connection pool maintained by thedatabase system, the connection usage information associated with afirst timeframe; determining an information type corresponding to theconnection usage information; based on the information type, selecting aparticular usage threshold from a set of usage thresholds; and based onwhether the connection usage information satisfies the particular usagethreshold, determining whether to adjust a size of the connection pool.18. The non-transitory computer readable medium of claim 17, wherein theinformation type corresponds to at least one of a short-term connectionusage information, long-term connection usage information, or a spikeconnection usage information.
 19. The non-transitory computer readablemedium of claim 17, wherein the information type corresponds to ashort-term connection usage information, and wherein the operationsfurther comprise: increasing the size of the connection pool based onthe short-term connection usage information satisfying the particularusage threshold;
 20. The non-transitory computer readable medium ofclaim 17, wherein the information type corresponds to a long-termconnection usage information and the particular usage thresholdcomprises a usage threshold range, and wherein the determining whetherto adjust a size of the connection pool further comprises: comparing thelong-term connection usage information with the usage threshold range.